Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-255342 | ASQL-00-010700 | SV-255342r879729_rule | Medium |
Description |
---|
Without the ability to centrally manage the content captured in the audit records, identification, troubleshooting, and correlation of suspicious behavior would be difficult and could lead to a delayed or incomplete analysis of an ongoing attack. The content captured in audit records must be managed from a central location (necessitating automation). Centralized management of audit records and logs provides for efficiency in maintenance and management of records, as well as the backup and archiving of those records. Azure SQL Database may write audit records to database tables, to files in the file system, to other kinds of local repository, or directly to a centralized log management system. Whatever the method used, it must be compatible with offloading the records to the centralized system. |
STIG | Date |
---|---|
Microsoft Azure SQL Database Security Technical Implementation Guide | 2023-06-12 |
Check Text ( C-59015r871150_chk ) |
---|
Review the system documentation for a description of how audit records are offloaded and how local audit log space is managed. From the Azure Portal Azure SQL Database page, select Auditing. Review the audit storage methods in use. If Azure SQL Database audit records are not written directly to or systematically transferred to a centralized log management system, this is a finding. |
Fix Text (F-58959r871151_fix) |
---|
Configure Azure SQL Database audit records to be written directly to a centralized audit storage location. https://docs.microsoft.com/en-us/azure/azure-sql/database/auditing-overview#audit-storage-destination To configure writing audit logs to a storage account, select "Storage" in the "Auditing" section. Select the Azure storage account where logs will be saved, and then open Advanced properties to select the retention period. Click "Save". Logs older than the retention period are deleted. |